Release 10.1A: OpenEdge Data Management:
DataServer for ODBC

The NO–WAIT option

The Progress 4GL NO–WAIT option specifies not to wait for a record that is currently locked by another process. Some ODBC data sources support this option and some do not. The following sections provide details.

DB2

DB2 does support the NO–WAIT option when the LOCKTIMEOUT option is set to zero.

Informix

Informix supports the NO–WAIT option by providing an equivalent NOT WAIT option.

Sybase

The NO–WAIT option works for DataServer applications in the same way that it works for OpenEdge database applications: the DataServer uses a time-out mechanism. If Sybase does not return a record within a set period of time, the DataServer considers the record to be locked. It then cancels the request to Sybase and sets the “locked” and “not available” conditions.

During a period of heavy demand, you might encounter situations where the “not available” condition is set although the record is not currently locked by a user. In this case, you might want to increase the time-out interval by using the -Dsrv RESP_TIMEOUT parameter.